Skip to content

[DBMON-6548] Add Mysql global wait_event query metric#23562

Open
eric-weaver wants to merge 2 commits intomasterfrom
eric.weaver/DBMON-6548
Open

[DBMON-6548] Add Mysql global wait_event query metric#23562
eric-weaver wants to merge 2 commits intomasterfrom
eric.weaver/DBMON-6548

Conversation

@eric-weaver
Copy link
Copy Markdown
Contributor

What does this PR do?

Adds a new set of metrics for events_waits_summary_global_by_event_name which will get us high level instance wide visibility into global wait event summaries. This will supplement the wait_events we track and surface within DBM from Query Samples by allowing us to get un-sampled wait_event data.

Motivation

Currently our wait event visibility is restricted to sampled queries. Since we sample in flight queries only and sample at a 1s interval, we currently miss visibility into many sub-second queries from samples. Having visibility into time spent instance wide in wait_events will allow us to remove some of the biased visibility we have from longer running queries and allow performance attribution to overall instance health trends.

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

@datadog-datadog-prod-us1
Copy link
Copy Markdown
Contributor

datadog-datadog-prod-us1 Bot commented May 1, 2026

Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

🎯 Code Coverage (details)
Patch Coverage: 96.43%
Overall Coverage: 90.15% (+2.99%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 5a3fc6a | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts
Copy link
Copy Markdown
Contributor

dd-octo-sts Bot commented May 1, 2026

Validation Report

All 20 validations passed.

Show details
Validation Description Status
agent-reqs Verify check versions match the Agent requirements file
ci Validate CI configuration and Codecov settings
codeowners Validate every integration has a CODEOWNERS entry
config Validate default configuration files against spec.yaml
dep Verify dependency pins are consistent and Agent-compatible
http Validate integrations use the HTTP wrapper correctly
imports Validate check imports do not use deprecated modules
integration-style Validate check code style conventions
jmx-metrics Validate JMX metrics definition files and config
labeler Validate PR labeler config matches integration directories
legacy-signature Validate no integration uses the legacy Agent check signature
license-headers Validate Python files have proper license headers
licenses Validate third-party license attribution list
metadata Validate metadata.csv metric definitions
models Validate configuration data models match spec.yaml
openmetrics Validate OpenMetrics integrations disable the metric limit
package Validate Python package metadata and naming
readmes Validate README files have required sections
saved-views Validate saved view JSON file structure and fields
version Validate version consistency between package and changelog

View full run

@codecov
Copy link
Copy Markdown

codecov Bot commented May 1, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.18%. Comparing base (cb90e62) to head (5a3fc6a).
⚠️ Report is 6 commits behind head on master.

Additional details and impacted files
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants